Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly parse double negation. #28497

Merged
merged 1 commit into from
Jan 31, 2025
Merged

Correctly parse double negation. #28497

merged 1 commit into from
Jan 31, 2025

Conversation

mikebenfield
Copy link
Collaborator

It should be a unary operation followed by a negative value.

Fixes #2555

@mikebenfield mikebenfield requested a review from d0cd January 30, 2025 21:34
Copy link
Collaborator

@d0cd d0cd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

It should be a unary operation followed by a negative value.

Fixes #2555
@mikebenfield mikebenfield merged commit 0e1f5ab into mainnet Jan 31, 2025
10 checks passed
@mikebenfield mikebenfield deleted the double-negation branch January 31, 2025 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Double negation of a field throws a compilation error
2 participants